The World of Computer Software/The World of Computer Software.iso/lnxd3-79.zip/DIGEST3.795

Internet Message Format | 1993-01-01 | 28KB

From [e-mail] Tue Dec 15 00:27:57 1992
Return-Path: <[e-mail]>
Received: from bloom-picayune (BLOOM-PICAYUNE.MIT.EDU) by montefiore.ulg.ac.be (4.1/SMI-4.1)
    id AA06116; Tue, 15 Dec 92 00:27:37 +0100
Received:  by bloom-picayune (5.57/25-eef)
    id AA29754; Mon, 14 Dec 92 17:46:19 -0500
Message-Id: <9212142246.AA29754@bloom-picayune>
From: Digestifier <[e-mail]>
To: [e-mail]
Reply-To: [e-mail]
Date:     Mon, 14 Dec 92 17:45:45 EST
Subject:  Linux-Activists Digest #795
Status: R

Linux-Activists Digest #795, Volume #3           Mon, 14 Dec 92 17:45:45 EST

Contents:
  Where is ``lint?''  ANSWER. (Joel M. Hoffman)
  Re: How do I provide the floppys to normal users???? (Joel M. Hoffman)
  Re: network over modem... (Daniel Russell)
  Re: [ANNOUNCE]: linux version 0.99 (see also: [BUG REPORT] swapping & sagas of X lockups) (Chris Newbold)
  Re: I have an interesting question... (Jonathan Magid)
  [Q] Linux and Notebooks (M.P. van Haarlem)
  Re: PCNFSD for Linux (Martin Braun)
  TCPIP-config (Michael Kraehe)
  Re: Suggestion Spliting Group (James Wiegand)
  Re: OS vs SYSTEM TYPE (long) [OS] (James Wiegand)
  Re: PCNFSD for Linux (Doug Beattie)
  IMPORTANT [BUG in 0.99] Re: [ANNOUNCE]: linux version 0.99 (Linus Torvalds)
  Re: QQ: bc on linux? (Charles Hannum)
  0.99 general protection error (Corey Minyard)
  Re: network over modem... (Matt Welsh)
  ANNOUNCE: Xcomm Patchlevel 5 available (Jeff Randall)
  newsreader for X (Dave Rose)
  BUG: xxgdb hangs X11 (Steven Samuel Jr. Seiden)
  Re: Optimal Partition Sizes (Thomas Dunbar)
  [comp.os.linux.announce] Welcome to comp.os.linux.announce! (Matt Welsh)
  Pros/cons of linux/386bsd? (Michael Harm)

----------------------------------------------------------------------------

From: [e-mail] (Joel M. Hoffman)
Subject: Where is ``lint?''  ANSWER.
Date: Mon, 14 Dec 1992 17:36:28 GMT

A few days ago I asked about ``lint.'' Several people wrote back
telling me that lint is not available, but that GCC will issue similar
warnings with the -Wall switch.

Thanks you to those who answered.

-Joel
([e-mail])

------------------------------

From: [e-mail] (Joel M. Hoffman)
Subject: Re: How do I provide the floppys to normal users????
Date: Mon, 14 Dec 1992 17:46:39 GMT

In article <[e-mail]> [e-mail] (Klaus Espenlaub) writes:
>Is there any possibility to give normal users the right to mount
>floppy drives???? I've been trying it with different success (it works only
>when floppys already in at boot time........)
>

Doing so would be a BIG security hole.  An ordinary user could mount a
floppy with a setuid-root shell, for example.  Running the shell would
be the same as having a ``su'' command with no password.

Of course, if users already have access to the machine, and to drive
a:, they can just boot from their own floppy, so the security problem
is there no matter what you do.

-Joel

------------------------------

From: [e-mail] (Daniel Russell)
Subject: Re: network over modem...
Date: Mon, 14 Dec 1992 18:09:27 GMT

[e-mail] (Matt Welsh) writes:

>It's called SLIP (Single Line IP), and it's currently in development for
             Oops (Serial Line IP)

 dan

------------------------------

From: [e-mail] (Chris Newbold)
Subject: Re: [ANNOUNCE]: linux version 0.99 (see also: [BUG REPORT] swapping & sagas of X lockups)
Date: 14 Dec 92 17:46:25 GMT

In <[e-mail]> [e-mail] (Rick Miller, Linux Device Registrar) writes:

>Okay everybody... You know the plan!  Linux 0.99 really *is* 1.0... but it'll
>need some bug-fixes before we *call* it 1.0.  So now is the time to concentrate
>on BUG FIXES.  I would even go so far as to suggest that the folks with other
>stuff they're doing under Linux (like everything other than the kernel) should
>concentrate on making their packages work with Linux 0.99...

Okay. I posted a note this morning about not being able to get 0.99 to boot.
Well, I solved that problem... Just my own stupidity. *BUT*, I may have a
bug to report here.

I also posted another note about X locking up perodically (Subject was
[BUG REPORT] swapping trouble ?!?). Now that I am running 0.99, the kernel
manages to keep limping when X locks up--enough for syslogd to spit out what
happens: I get a whole bunch of "No free inodes -- contact Linus" messages.

==>> Before you tell me one of my filesystems is full, read this: I did an
==>> fsck/efsck -v on all my paritions; none have inode usage over 30%.

My thoughts are that there is a problem with the number of open files. What
is the current limit? When running X, I see the number of open files up around
300. However, it never gets higher--if I do something which opens a file,
X hangs and I get the "No free inodes messages."

I can recreate this quite easily by trying to run two copies of ghostview
at once.

I would really like to get this fixed--even if I get a bunch of mail telling
me I'm a bonehead because I've done something wrong.

-Chris

--
>>>> Chris Newbold <<<< * "If you fool around with a thing for very long you *
University of Rochester *                 will screw it up."                 *
Disclaimer: "All warranties expire upon payment of invoice."
[e-mail] * uhura.cc.rochester.edu!ctne_ltd@uunet

------------------------------

From: [e-mail] (Jonathan Magid)
Subject: Re: I have an interesting question...
Date: Mon, 14 Dec 1992 18:18:24 GMT

In article <[e-mail]> [e-mail] (Jerry Jeremiah 290-8941) writes:
>I want to know if, while we can mount dos volumes, can we mount disks
>that have been stacked with Stacker or DoubleSpaced with MSDOS 6.0?
>
>(btw, the MSDOS 6.0 is a beta version and is not out until next year)
>
>>>Jerry

There was a recent success story on this, and I'll try to post how to do
it from memory

(DISCLAIMER: I have never tried this and do not run stacker.  I suspect
this whole kludge could lead to you losing all of your data if something
goes wrong: THIS IS AT YOUR OWN RISK)

now that my butt is covered, lets try this.

get the dos emulator: it comes with SLS and other wise is in the ALPHA
section of the Linux archives (btw, this emulator is actually PRE alpha)

for DOS 5.0 (and 6.0? I don't know, but probably) and DR-DOS 6.0 find the lines

        printf("general protection\n");
        error=4;

and change 4 to 0.  this will keep some skull duggery from Microshaft from
crashing the emulator on startup (no flames please.  Microsoft's history
of providing these wonderful services in their OS's is well documented.
ask the FTC.)

now compile the emulator and set it up per its accompanying instructions.

with a dos system disk in the drive, run

        dos a > errors.log

change directories to c: you should see LINUX.EXE which you should
run.  This will turn your dos partition (which should be mounted when
you start to /usr/dos) to a d: drive.

if you change there you should see all of your uncompressed files, including
STACKER.COM (or whatever it is called) and the big file that is really
your stacker volume.  run stacker.com.

this should do it.  again a disclaimer: i have neither tried this nor
think its a particularly good idea.  if you must go where angels fear to
tread then at least try it on some sort of test partition first.  the
emulator is *really* flakey and stacker is magical. flakey magic is dangerous!


good luck,
jem.



--
Jonathan Magid     [e-mail]       sunSITE Administrator
Virtual pizza Delivery (tm)::faxed in 30 cycles or less or you get it
========================================FREE!!!=======================

------------------------------

From: [e-mail] (M.P. van Haarlem)
Crossposted-To: comp.sys.laptops
Subject: [Q] Linux and Notebooks
Date: 14 Dec 92 16:50:38 GMT


Hello people,

I am thinking about buying a notebook and plan to run Linux on it. I
have not yet decided which one. At the moment I am leaning towards a
486SX or DX, 8Mb, Mono, 120+Mb HD. I have some info on the IBM
ThinkPad 700, Texas Instr. 4000 Series and Toshiba 4400 SXL. Does
anybody out there have any experience with these machines and Linux.
(Perhaps a naive question, but is the IBM TrackPoint of any use under
Linux).

What about other (cheaper) notebooks. I have noticed that in the 486
range there are not nearly as many available in the Netherlands as in
places like the UK or US. Has anybody failed in installing Linux on
any notebook.

Answers either to the net (I'm sure quite a lot of people are interested
and most of the previous questions relating to notebooks and Linux have
never been summarised. If I get enough responses I'll post a summary.)
or to  ...  [e-mail]

Thanks,
Michiel

--
Michiel van Haarlem, Leiden Observatory, [e-mail]

------------------------------

From: [e-mail] (Martin Braun)
Subject: Re: PCNFSD for Linux
Date: Mon, 14 Dec 1992 18:59:34 GMT


Hello all,

I have compiled pcnfsd without major problems. You will need
the RPC - library port by Rick Sladkey ([e-mail]).
It is available as sunrpc-bin-4.0.tar.Z on many linux sites
in the ALPHA/NFS directory. Your kernel must have NFS - support
compiled in. I use the sources from SLS (0.98p5) with all patches
from the package lxpatchs.taz on disk b4 applied.
The changes to pcnfsd.c consist of checking some file and directory
names, supplying a mode in some
mkdir calls, declaring the crypt() function and changing the
type of free_list() to void.
To install pcnfsd on your system add it to your rc.net script
after the other NFS stuff. Remember to add your pc to /etc/exports
so that it is allowed to do mounts.
Since it has only been a short time that I've been using this,
I can't tell how stable it is. I couldn't get printing via NFS
to work yet (the jobs get queued but are truncated to length zero).
I'll post some more on this if there is interest.

Hope this helps,

Martin Braun
[e-mail]

------------------------------

From: [e-mail] (Michael Kraehe)
Subject: TCPIP-config
Date: Mon, 14 Dec 92 13:35:00 GMT

Hy folks,

I think config is a bad name for that tool, after a find -name config
i fount 3 executabels and 2 other files.

Wy dont we name it ifconfig or sock_config, to avoid naming conflicts with
BSD.

By Michael.

------------------------------

From: [e-mail] (James Wiegand)
Subject: Re: Suggestion Spliting Group
Date: 14 Dec 92 16:24:13 GMT

In article <[e-mail]> [e-mail] (Stephen R. Phillips) writes:
>
>Stephen R. Phillips ([e-mail]) wrote:
>:
>: In hopes that this will prevent the 99-300 message per day from
>: SWAMPING most poeple.  I suggest this group be split.
>
>PLEASE do not reply or follow up to this message any longer I am canceling it.
>I guess I missed the CFV and voting on this topic.  I will no longer
>read this group since:
>1:     The traffic is rediculous
>2:     No comment.
>
>No flames are needed I apologize for posting this.
>
>This means the subject is closed I will NO longer reply to mail for
>this either.  So if you get bounced it's because I bounced it and the
>subject matter is closed as far as I'm concerned.
>
>Cyberman

Nice guy, huh? That's it, start a flame war and run for cover.

jim

------------------------------

From: [e-mail] (James Wiegand)
Subject: Re: OS vs SYSTEM TYPE (long) [OS]
Date: 14 Dec 92 16:47:22 GMT

In article <[e-mail]> [e-mail] (Bill Riemers) writes:
>
>After reading through all those back articles in both comp.os.linux
>and comp.os.bsd I've come to the conclusion the best thing for a
>new user to do would be to install MSDOS, LINUX, and 386BSD on thier
>computer.  However, it sounds like you have to reboot your computer
>everytime you want to change your system type!  This might seem
>reasonable until you stop and ask yourself what is the purpose of
>an OS?  Mind you my understanding (mind you I am not a computer
>scientist) is that an OS is what provides an interphase between
>software and hardware for all programs.  That is why on an APOLLO
>computer I can switch readily between the system types of
>BSD4.2, BSD4.3, SYS5.0, SYS5.3, and AEGIS without rebooting the
>machine.  (Even without re-loging in.)  All of these system types
>work through DOMAIN-OS.
[ ... ]
>The way this swapping of system type works on APOLLOs is:
>
>   ver system-type command   ==> excutes one command in the
>                                 selected system type
>
>   ver system-type           ==> switches to the selected
>                                 system type
>
>The system SYSTYPE tells the OS what type of system you are
>operating in.  So rather than having a root '/bin' directory, you have:
>
>  '/sys5.3/bin'
>  '/bsd4.3/bin'
>

Here at Temple we have an Apollo ring (and I use that term loosely), so I
am somewhat familiar with what you are saying. One summer, they spent
a year upgrading to Domain 10.2 (the first Unix-y release they installed).
The problem is, the Apollo systems run Domain as their native operating
system (exec, file systems, ACL, window managers) and everything else
is layered on top. This brought programs like the print spooler,
IDEAS, and ANSYS to their knees. Print jobs whent from 10 min. to 40+ min.
The operating system doubled in size and swapped much more frequently.
This was on a network that already had space problems!

The point is, a system like this takes a 50% - 60% performance hit.
Having user-mode programs like the DOS-emulator is better since you
only take the performance hit when you need to. When you build it
into the kernel, there is NO way around it.

Besides, I don't think any of the gurus would write such a beast anyway.

jim
whose only affiliation with Temple is being one of their students.

------------------------------

From: [e-mail] (Doug Beattie)
Subject: Re: PCNFSD for Linux
Date: 14 Dec 92 18:35:01 GMT
Reply-To: [e-mail] (Doug Beattie,D1V03,6814)

In article <[e-mail]> [e-mail] (Ed Boston)  writes:
>Does anyone know if there is a PCNFSD available for Linux?  I have been
>watching some of the discussions of Linux and would like to set it up,
>but I would need this ability for my needs.
>
>Ed
>---
> . OLX 2.1 TD . AAcckk!!  II''mm iinn hhaallff dduupplleexx
>

Sun's East Coast Group provides the PCNFSD daemon in source form that should
be available at bmc.tmc.edu.  I believe that the latest release that Geoff,
Sun's Engineer, released was pcnfsd.92.11.05.tar.Z.  If you have problems
getting one that should compile and work, let me know and I'll try to get
it to you.

--
Doug Beattie - Computer Development Services Inc.       (UUCP)   sun!unislc!dbb
c/o Unisys Corporation                                [e-mail]
322 No. 2200 West   M.S. D1V03         Subcontractor 88K MP NFS Group - SLC, UT
SLC, UT 84116  [phone]   Disclaimer - I represent myself and no one else

------------------------------

From: [e-mail] (Linus Torvalds)
Subject: IMPORTANT [BUG in 0.99] Re: [ANNOUNCE]: linux version 0.99
Date: 14 Dec 92 19:22:04 GMT

Simple but important bug-fixes follow.  Please check them out if you
have had problems with 0.99.

In article <[e-mail]> [e-mail] (Chris Newbold) writes:
>
>Okay. I posted a note this morning about not being able to get 0.99 to boot.
>Well, I solved that problem... Just my own stupidity. *BUT*, I may have a
>bug to report here.
>
>I also posted another note about X locking up perodically (Subject was
>[BUG REPORT] swapping trouble ?!?). Now that I am running 0.99, the kernel
>manages to keep limping when X locks up--enough for syslogd to spit out what
>happens: I get a whole bunch of "No free inodes -- contact Linus" messages.

Good.  I added code to handle the "out of inode" error more gracefully,
and it seems to have found the error pretty efficiently (well, I
suspected it already, which is why I wrote the code in the first place,
but now it's confirmed).  Consider me contacted.

Sadly, the "out of inode" code has a silly bug that can lead to kernel
panics at bootup: the 'inode_wait' wait-queue is not correctly
initialized to NULL, so people booting from floppy may get bad values
here. So here are a couple of fixes for 0.99 - unofficial, but I would
like to hear if there are still problems after these:

 1) in linux/fs/inode.c, at the start, change

        static struct wait_queue * inode_wait;

    to

        static struct wait_queue * inode_wait = NULL;

 2) in linux/include/linux/fs.h, double the value of NR_INODE (to 256),
    ie change

        #define NR_INODE 128

    to

        #define NR_INODE 256

and see if that is enough (it really should be: NR_FILE is 128, so the
above value for NR_INODE should leave plenty of inodes for things like
executables etc).  Hopefully you won't get the "No free inodes" problem
any more.

Note that I'll have to make the number of inodes dynamic, but I won't do
so for 1.0, as the changes would be big enough to be bug-prone.  1.0
need not be perfect, but I hope it will be stable.

                Linus

------------------------------

From: [e-mail] (Charles Hannum)
Subject: Re: QQ: bc on linux?
Date: 14 Dec 1992 18:54:19 GMT


In article <[e-mail]>
[e-mail] (Keith Fuller) writes:
>
> Has anyone written bc, the arbitrary precision calculator for linux?

The GNU version should work.

--

------------------------------

From: minyard@crchh7b9 (Corey Minyard)
Subject: 0.99 general protection error
Date: Mon, 14 Dec 1992 18:14:05 GMT

The default 0.99 kernel gave me a general protection at startup.  The kernel
was crashing in wake_up().  After some creative debugging (I added a stack
trace-back to the exception handler) I found the bug was coming from iput().
It turns out that the inode_wait variable was not being initialized to NULL.

Make the following change the following in fs/inode.c to fix the problem.
This is not really a diff, but you should get the idea:
***
  static struct inode inode_table[NR_INODE];
  static struct inode * last_inode = inode_table;
! static struct wait_queue * inode_wait;

  void inode_init(void)
  {
***
  static struct inode inode_table[NR_INODE];
  static struct inode * last_inode = inode_table;
! static struct wait_queue * inode_wait = NULL;

  void inode_init(void)
***

Corey
[e-mail]

------------------------------

From: [e-mail] (Matt Welsh)
Subject: Re: network over modem...
Date: Mon, 14 Dec 1992 19:07:14 GMT

In article <[e-mail]> [e-mail] (Daniel Russell) writes:
>[e-mail] (Matt Welsh) writes:
>
>>It's called SLIP (Single Line IP), and it's currently in development for
>            Oops (Serial Line IP)


Yeah. I guess "Single Line" doesn't make a lot of sense. :)

mdw

--
Matt Welsh     [e-mail]     Cornell Theory Center
  "Go on, emote! I was raised on thought balloons!"

------------------------------

From: [e-mail] (Jeff Randall)
Crossposted-To: comp.os.linux.announce
Subject: ANNOUNCE: Xcomm Patchlevel 5 available
Date: 14 Dec 92 19:18:22 GMT
Reply-To: [e-mail] (Jeff Randall)

I was asked to upload the new patchlevel of Xcomm by the author.
These files superceed the old packages.


The Two files are xcomm3b-L1.5.src.tar.Z and xcomm3b-L1.5.bin.tar.Z

The binary package contains a striped binary linked with jumptable 4.1
with the new stat() call and the source used to compile it. The source
package contains just the source used to compile the binary in the bin
package.

below is the message sent to me by the author and is also included in the
packages.

===========

Subject: Re: xcomm patchlevel 1.5
To: [e-mail]
Date: Mon, 14 Dec 92 0:49:22 EST
From: Thomas McWilliams <bimbo!ukelele![e-mail]>
Reply-To: pyrdc!bimbo!ukelele![e-mail]


Hi Jeff,

> It seems to work fine.. you mentioned that you did not have FTP access,
> did you want me to put it at tsx-11 and sunsite?

Yes, could you do that for me? I would appreciate it *very* much.
That was the reason it hasn't been updated there in a long time.
I am going to sign up with holonet but since that is untested I would
think it best to trust you to move it to the FTP sites. You might
want to make a mention of it in comp.os.linux and I will post a
message also describing the changes.

Basically the changes are:

a) bug fixes,
b) clean-up of the code,
c) correction of the buffering problem with stderr (a fault of GCC 2.x),
d) fixes to the dialing directory to not choke on the DEL character,
e) improved dos_mode for displaying high-ascii characters and line graphics
   (the latter by mapping them to vt102 graphics sequences),
f) proper parsing of dos-type "ansi" (?) sequences which differ from the
   vt102 standard.
g) *selectable* trapping of the DEL character and mapping it to backspace.

It should be noted also that the internal xmodem protocols are considerably
improved and faster than stock XC. I should get around to submitting my
patches ..... :-)

If you have any suggestions, just drop me a line.

Thanks again,

Thomas

Replies to: uunet!pyrdc!bimbo!ukelele!tmcwill

--
[e-mail] (ASCII mail)           THIS IS _NOT_ CCSO'S OPINION!!!
[e-mail] (NeXT mail)      If It were, It would've had a
[e-mail] (anon)                  more important name on it. =)

--
Send submissions for comp.os.linux.announce to: [e-mail]

------------------------------

From: [e-mail] (Dave Rose)
Subject: newsreader for X
Date: 14 Dec 92 12:18:03 GMT

Does anyone have a decent newsreader for X compiled for Linux?
Any suggestions on where to look?

------------------------------

From: [e-mail] (Steven Samuel Jr. Seiden)
Subject: BUG: xxgdb hangs X11
Date: 14 Dec 92 19:31:24 GMT

I'm using the SLS .98.5 distribution, pretty much as is,
(got olvwm though) and I've had problems with xxgdb.
My config is:

33Mhz 386 w/ Cyrix Cop.
12 Meg Ram - No swap
80 meg HD

I'll be running xxgdb, when all of the sudden the
screen switches back into text mode. The cursor is
in the lower left hand corner. Other than this, the
screen is blank. Nothing I type appears on the screen,
although the disk whirls when I type sync. I haven't had
this problem when I wasn't running xxgdb, so I'm pretty
sure that xxgdb is at fault (although not completely).
My solution has been to stop using xxgdb. I've never
had this problem running plain gdb. Anyone else had this
problem? Any suggestions?


--
Steve Seiden                                     Information & Computer Science
[e-mail]                            University of California, Irvine
                        Just say No to MS-DOS

------------------------------

From: [e-mail] (Thomas Dunbar)
Subject: Re: Optimal Partition Sizes
Date: 14 Dec 92 19:39:55 GMT


 a safer way to use ext fs is to have one ext partition and symlink to it
when one needs >14char filenames. i use a 10M ext (40M root:basic & src;
64M /usr for TeX,X11,Emacs, etc)
  thomas

------------------------------

Crossposted-To: comp.os.linux.announce,news.answers
From: [e-mail] (Matt Welsh)
Subject: [comp.os.linux.announce] Welcome to comp.os.linux.announce!
Date: Mon, 14 Dec 1992 20:22:53 GMT

Archive-name: linux-faq/announce/intro
Last-modified: 6 Dec 1992

WELCOME TO COMP.OS.LINUX.ANNOUNCE!

Comp.os.linux.announce (which has a nifty acronym: "c.o.l.a") is a
newsgroup for announcements, important information, and software patches
for the Linux operating system, a free UNIX clone for i386 and i486 based
machines.  This group is a moderated companion to comp.os.linux, which is
the group for discussions, questions, and general information about Linux.

This group has been created to provide a seperate group in which to crosspost
important information about Linux, since these postings are often lost in
the heavy bandwidth of comp.os.linux. In general, postings to c.o.l.a will
also be posted to comp.os.linux, for those who receive c.o.l over the FidoNet
gateway and other non-USENET sources.

The moderators for this group are myself (Matt Welsh, [e-mail]) and
Lars Wirzenius ([e-mail]). We will be sharing the moderator
duty, and backing each other up to make sure that postings to this group will
be approved as soon as possible after they're submitted.

Submissions to this group should be mailed to the address:
        [e-mail]

If you have any problems or questions about c.o.l.a, please send mail to the
moderators at
        [e-mail]
Or simply mail us directly.

A seperate posting details the guidelines for submitting to this group.
I plan to approve just about anything that's posted to this group, except for
questions or discussions about Linux. So, please, post away.  :)

Plans are in the works for having this group archived at one or more of
the Linux FTP sites; more on that later. I also plan to start a mailing
list channel for those without USENET access (when the linux-activists
list is going again).

Matt Welsh
Comp.os.linux.announce moderator
Submissions to: [e-mail]

--
Matt Welsh     [e-mail]     Cornell Theory Center
  "Go on, emote! I was raised on thought balloons!"

------------------------------

From: [e-mail] (Michael Harm)
Crossposted-To: comp.unix.bsd
Subject: Pros/cons of linux/386bsd?
Date: 14 Dec 1992 11:50:18 -0800

Hi folks.
We are trying to decide whether to go with linux or 386bsd for
our 486 machines.  Particular constraints are:

We don't have a lot of disk space.
We need X11.
We don't have a lot of memory per machine.
We don't have cd roms

Any information on the relative strengths/weaknesses of these
two systems would be a big help.  Please email info to [e-mail]

Thanks much!

Mike Harm
[e-mail]
Univ. of Southern California
===============================================================
"I agree that 'two times two makes four' is an excellent thing;
but if we are dispensing praise, then 'two times two makes five'
is sometimes a most charming little thing as well."
                 -Fyodor Dostoevsky,   "Notes From Underground"

------------------------------


** FOR YOUR REFERENCE **

The service address, to which questions about the list itself and requests
to be added to or deleted from it should be directed, is:

    Internet: [e-mail]

You can send mail to the entire list (and comp.os.linux) via:

    Internet: [e-mail]

Linux may be obtained via one of these FTP sites:
    nic.funet.fi                pub/OS/Linux
    tsx-11.mit.edu                pub/linux
    tupac-amaru.informatik.rwth-aachen.de    pub/msdos/replace

The current version of Linux is 0.98pl6 released on December 2, 1992

End of Linux-Activists Digest
******************************